In subobject mode, when you toggle the bounding box and make it fit the main object, it would be nice if the dimensions of the box would be displayed. It would make it easier to know the dimensions of the car.
4.2.1
Version 4.2.1 is out with the new IS_IPB packet introduced in LFS 0.7F.
Only plain IPv4 strings are supported for now, but if there's demand for more advanced conversion/parsing, feel free to give feedback.
The IP strings go through validation before the packet is sent. If it's not a valid IPv4, a RangeError will be thrown.
Set new IP bans:
Request all IP bans:
Only plain IPv4 strings are supported for now, but if there's demand for more advanced conversion/parsing, feel free to give feedback.
The IP strings go through validation before the packet is sent. If it's not a valid IPv4, a RangeError will be thrown.
Set new IP bans:
inSim.send(
new IS_IPB({
BanIPs: ['1.2.3.4', '2.2.2.2', '5.5.5.255'],
}),
);Request all IP bans:
inSim.send(
new IS_TINY({
ReqI: 1,
SubT: TinyType.TINY_IPB,
}),
);
inSim.on(PacketType.ISP_IPB, (packet) => {
console.log(packet.NumB); // 3
console.log(packet.BanIPs); // ['1.2.3.4', '2.2.2.2', '5.5.5.255']
});
Last edited by Flame CZE, .
I'm curious what progress Eric has made regarding the track updates and even the new tracks. Last report from him was in the 20th anniversary news article from 2022. Are the existing tracks fully updated now, or are there still some holes to fill? It would be nice to see some screenshots if there is something new to show.
In the IS_NCI packet, the IPAddress property is "unsigned". It's also a 4-byte integer so it should work the same, but is there a reason why it's not "in_addr" too?
A minor mistake in InSim.txt on line 1171 (new IS_IPB packet):
It should be:
It should be:
I can't find the download link for the LFS Editor patch 
But those DRS are only visual and do not affect the actual downforce.
Version 8
Finally got out of WIP 
Added an LOD2 model
Fixed the aspect ratio of the front number plate
Added an LOD2 model
Fixed the aspect ratio of the front number plate
What’s the point of this thread? I don’t see anything in progress, it seems finished already 
You can also test it by setting the longest possible text in the numberplate field and checking if all letters fit in that area.
Good effort!
I’d suggest to include a copyright usage license like you see on Sketchfab for instance, so modders would know if its ok to use in LFS mods and under what conditions. It would also be more transparent for the reviewers.
I’d suggest to include a copyright usage license like you see on Sketchfab for instance, so modders would know if its ok to use in LFS mods and under what conditions. It would also be more transparent for the reviewers.
Maybe there could be a descriptive error message to explain what happened instead an unhandled exception.
The .ban files in move folder
It is a limitation of LFS physics. The physics contact points are only placed at the bottom of the tyre, when the car is level with the ground. Other parts of the tyre don't have any collision detection.
The driver animations are always tied to the steering angle, the lean angle cannot be controlled independently.
Changes in version 6:
Updated suspension geometry:
- upper and lower pivots are closer together so the wishbone arms are not parallel anymore
- thrust bearings are higher and closer to the
car centerline
- raised rear max up value to 0.3 m for more available travel
Updated default setup:
- added more stiffness
Hopefully the car is more stable now and does not bottom out as much. Feedback is welcome
Updated suspension geometry:
- upper and lower pivots are closer together so the wishbone arms are not parallel anymore
- thrust bearings are higher and closer to the
car centerline
- raised rear max up value to 0.3 m for more available travel
Updated default setup:
- added more stiffness
Hopefully the car is more stable now and does not bottom out as much. Feedback is welcome
You can control local car lights by sending an IS_SMALL packet with a SubT of SmallType.SMALL_LCL. For example, to turn the high beam on, you send this packet:
Handling commands is done by setting the command prefix character in the inSim.connect() method config and then listening for the IS_MSO packet.
I have created a demo application where you can type !lights on or !lights off to toggle the car's high beam. You can check the full source code at github.com/mkapal/node-insim-car-lights-example. The main program code is in index.ts. Feel free to clone the repository, follow the instructions in the README file and see if it works for you.
inSim.send(
new IS_SMALL({
SubT: SmallType.SMALL_LCL,
UVal: LocalCarLights.LIGHTS_HIGH,
}),
);
Handling commands is done by setting the command prefix character in the inSim.connect() method config and then listening for the IS_MSO packet.
I have created a demo application where you can type !lights on or !lights off to toggle the car's high beam. You can check the full source code at github.com/mkapal/node-insim-car-lights-example. The main program code is in index.ts. Feel free to clone the repository, follow the instructions in the README file and see if it works for you.
Last edited by Flame CZE, .
Looks like he's only using the screenshot as a reference image, not tracing a 3D model extracted from a game, so it should be fine.
You can download a fresh LFS installation from the downloads page, install it in a different directory and copy&paste the LFS_restart.exe file from there.
LFS_restart.exe is used for automatically restarting LFS after installing an update via the in-game auto updater.
LFS_restart.exe is used for automatically restarting LFS after installing an update via the in-game auto updater.
Thanks!
I think I will try to replicate something similar using my React Node InSim library because I’m not familiar with Lapper.
Do you think I could use your sign buttons in my app? I would credit you of course.
I think I will try to replicate something similar using my React Node InSim library because I’m not familiar with Lapper.
Do you think I could use your sign buttons in my app? I would credit you of course.
You can specify a range of IPs as well. For example 123.123.123.0/24 will allow all IPs from 123.123.123.0 to 123.123.123.255.
That's actually cool! I've wanted to do something like this for a "driving lessons" style InSim. Is it still available to download?
In Access Control - "Allow IP addresses to the InSim port", you probably have more than 8 IP addresses or ranges set. It seems like there is a limit now.
FGED GREDG RDFGDR GSFDG